This is the second beta release, fixing a major bug that caused more powerful Macs to crash, especially after hitting the Dial button or at the end of a connect. Also, EMSI is able to accept multi-address packets now. Balloon help has been added.
CONTENTS: * 1. Introduction
* 2. Configuring Charon
* 3. Using Charon
* 3. Some typical setups
* 4. Notes for this beta version, solving problems
ACKS:
Zmodem Sources: Bit Bucket Software Co, the Zmodem code from Binkley 2.50
EMSI Sources: based on Anthony Rumble's Unix pointmailer NixMail 0.05a
System 7 and Tough Apple Stuff: Peter Kocourek
Fido related Expert Advice: Stefan van Dessel
DISCLAIMER DEPARTMENT:
Responsibility for damage caused by the use of Charon lies with the user only. No profit may be made by distributing Charon (freeware distributors may not charge more than $6 for the disk that contains Charon, including the disk itself and postage) without prior permission by the author.
QUESTIONS & COMPLAINTS:
* Oscar Vermeulen, Hildebrandhove 108, 2726 AZ Zoetermeer, the Netherlands.
* Phone (voice, no modems, please): +31-79-213312
* Usenet: oscar@nu91.wlink.nl (valid until dec.93), Fidonet: 2:281/527.18
* Please let me know if something is not working as it should.
Charon is a 'freeware' fidonet pointmailer featuring the standard EMSI and YooHoo protocols and fast ZedZap (zmodem) file transfers. It is designed to be used together with CounterPoint or Alice (v2.21 upwards), or to serve as a replacement for MacWoof's built-in mailer. Other message editors should work as well.
Some pro's of Charon:
1) Up-to-date connects with DOS-based mailers, using EMSI (multi-address
ability for those who need it) and efficient, reliable ZedZap transfers,
2) no shareware fee,
3) simple to install and use.
Some cons:
1) a pointmailer is only useful for point setups: it will NOT answer incoming calls.
2) this is a beta release, so there are supposed to be bugs and imperfections.
3) no FTS-0001 support. FTS-0001 was the original Xmodem based fidonet protocol,
which was more or less replaced by YooHoo and EMSI some years ago.
The third point needs some elaboration. Charon has been tested with practically every fidonet mailer in use today. Tabby is the only one that will not work, since it recognises only the FTS-0001 protocol.
Now that Mac BBS systems are gradually replacing Tabby with Formula 1, I'm not bothered too much by this incompatibility. Besides, MacWoof already serves as a decent FTS-0001 mailer if you do need to connect with Tabby.
The Charon & Obolus combo:
-------------------------
Obolus is a mail exporter for CounterPoint, developed by Peter Kocourek. Charon can use it to automatically extract the messages you wrote in CounterPoint, right before dialing your boss. In everyday use, Obolus runs almost invisibly from within Charon. Its use is entirely optional, but recommended for CounterPoint users.
Babble:
-------
Charon was bolted together as a piece of freeware using the following sources:
Zmodem Sources: Bit Bucket Software Co, the Zmodem code from Binkley 2.50
EMSI Sources: Anthony Rumble, from his excellent Unix pointmailer NixMail 0.05a
A Big Thank You to these authors. In accordance with their Copyleft scheme, Charon's sources are available from me upon request, with the provision that you do not use them to make another *point*mailer.
Thanks also to Peter Kocourek, for providing me with some of the toughest Mac code in Charon, and for writing Obolus. Experts in Greek mythology will not be surprised that Charon and Obolus were developed to work together. They will also know our opinion regarding the DOS-based world on the other side of the phone line...
The basic idea behind Charon is very simple -- Charon sends all files (normally, .pkt files) that are placed in an outbound folder to its Boss, and puts all files offered by its Boss in an inbound folder. A configuration file is used to store all necessary information.
Installing Charon is a matter of creating a config file for every fido system you want to call. To create your first config file, select 'Add a new Boss' in the File menu. After this first config file is saved to disk, you can create new ones much more quickly by selecting 'Edit Boss Config'.
Charon does not check your configs for errors. The information you enter in the three dialogs that follow 'Add a new Boss' has to be right to let Charon do its work, so be careful. Balloon Help is available for system 7 users.
2.a. -- The POINT SETUP dialog:
-------------------------------
This dialog first asks for your point's name and other information required for a successful fido connect. Also, here you can set up your modem. Use your own favourite modem-init string, but be sure to include X3E0 (zero, not the letter) at the end of the string. If you suffer from sudden disconnects, add &D0.
2.b. -- BOSS SETUP dialog:
-------------------------------
This dialog wants some data specific to your boss's system:
1) Your boss's address (which is used as the filename for the config file),
2) Its name and telephone number,
3) Your password (if used),
4) Your own point address. If you want to present more than one address to your boss (useful with EMSI systems only), enter them all, separated by ONLY a single space, as in the default example.
--'Try EMSI before YooHoo': keep this checked at first. If you notice that Charon mentions YooHoo anyway when calling your boss, uncheck this to speed things up.
--INBOUND Folder: where to store received files.
a) using CounterPoint or Obolus: select CounterPoint's 'PKT's' folder.
b) MacWoof: Select the folder Woof shows when you select 'File->import'.
--OUTBOUND Folder: Charon transmits ALL files found in this folder.
a) for CounterPoint: Use Counterpoint's 'Gateway' folder,
b) MacWoof: use an empty folder to store outbound packet files.
c) for CounterPoint+Obolus: Slight complication. Obolus creates a folder called '2.281.527' (or whatever the address of your boss is) the first time it exports mail. If you cannot find this folder, create it yourself and tell Charon this is the outbound folder. (NOTE that in Obolus itself, you enter the parent folder of 'x.xxx.xxx' as the outbound folder, as it assumes 'x.xxx.xxx' automatically. Confusing indeed, sorry.)
--OBOLUS (if used): Select the Obolus program file. This will start Obolus before your boss is called to create outbound files. NOTE: be sure _not_ to check 'run Charon' in Obolus' own config.
2.c. -- DECOMPRESSION Dialog:
---------------------------
Charon can decompress inbound mail packets. It does so by calling either ZipIt (ZIP) or AutoUnArj (ARJ) right after polling your boss. AutoUnArj, by the way, is a modified version of unArj Mac, the original Mac port by Erik Larson. I can send you a beta version upon request.
If you use some other decompression program, select it as an AutoUnArj program, and set the file type and creator to whatever your program desires. The program will be started from Charon automatically, though you'd have to do the rest.
NOTE: Only files with the standard fido filename extensions .mo?…. .su? (i.e., 00fe5c3e.mo1) are considered to be compressed inbound mail. Other files (received as result of a file request, for instance) are not decompressed by Charon.
PHEW....
-------
After you're done with the three dialogs, Charon lets you save the config file. The filename HAS to be the address of your boss, something like 1.362.452. Use the default name Charon offers you, or if you like, a fake address (that does not interfere with anything in the current version). This trick allows you to have more than one config file for the same boss, too.
Simply double-click the appropriate config file (put it on your desktop to have it at hand?) and hit the Dial button. Alternatively, run Charon, hit Dial, and select the config file. If you selected so, Obolus will be run before dialing out to prepare the outbound mail.
You can always abort the polling process by hitting [command]-[.]. Aborted Zmodem transfers will be resumed automatically at the next poll. During Zmodem transfers, the effect of cmd-. may be slow in coming.
If you selected a decompression program to be used, Charon deletes the compressed packets after it has ascertained decompression was successful. As a measure of precaution, you can still find the deleted files in the trash can.
Freqs and File Attach messages:
-----------------------------
File Requests: Your message editor creates a standard .REQ file. Just put it in the outbound folder. File Attaches: Create a file attach message, and drop the attached file in the outbound folder. If you want to attach programs, convert them to MacBinary format, or use a compression program like ZipIt.
Registration:
------------
Charon is freeware, so registration is just a formality. It is 'required' nevertheless, just to satisfy my own curiosity... All it takes is a few seconds, simply use the Special->Registration menu item to create an automatic netmail to me. Thank you!
My own favourite point setup consists of Charon, AutoUnArj or ZipIt (whatever your boss uses to compress received packets), CounterPoint, and Obolus (which enables Charon to extract outbound messages all by itself).
This is, however, no more than my personal opinion. You can skip Obolus, or use MacWoof as a message editor, or use any other software (I still use a message editor running under Soft PC, for instance....). Charon just looks for packets to send, and doesn't care.
a. Setting up CounterPoint to work with Charon:
--------------------------------------------
Read CounterPoint's 'MacWoof Setup' text file (or just select MacWoof as CounterPoint's mailer). Everything's the same for Charon, BUT:
- Put Charon in the CounterPoint folder. Select Charon as
CounterPoint's System Paths '1st Launch' item.
- Poll your boss using CP's 'Call Remote System' menu item. This
will export your outbound mail and start Charon. Hit Charon's
Dial button to start.
b. Setting up CounterPoint and Obolus to work with Charon:
Just as described above. But - run Charon from the finder (otherwise CP will do the exporting itself before Obolus gets a chance) any time you feel the urge to call your boss; you don't need to bother with creating/exporting .pkts. Obolus does that automatically from within Charon.
c. Setting up MacWoof to work with Charon:
-----------------------------------------
Use 'Import' and 'Export' in Woof's File menu to create outbound packets and to process inbound packets. Note that Charon is useful only if your boss doesn't use Tabby. Because it uses zmodem transfers, Charon is slightly faster than MacWoof, and offers more secure transfers (aborted transfers are resumed automatically, for instance).
Thanks for trying Charon! I'm not an expert Mac programmer (God forbid), so there are bugs for sure. I wrote Charon for my own use, originally, and I do not pretend this is a professionally designed program. It is thoroughly tested by now, though, and it certainly won't eat your mail.
I decided to release a beta version now, because I will be (cruelly) separated from my Mac for some time to come - and this version is reliable enough to be of use to normal users. At the end of this year (1993), I hope to come up with a final version.
Charon has been tested successfully with FrontDoor, Binkley, D'Bridge, Binkley ST, TheBox ST, TheBox PC, Dutchie, Intermail and Formula 1 systems. If you encounter a bug nevertheless, please save the SerialLog file and mail it to me. Also, maybe you can try if the bug can be reproduced, and look at the information that appears with Debug Stuff selected (just click on the miniature button in Charon's main window).
Known bugs:
- This manual. Due to a lack of time, this doc is not as user-
friendly as it should be. I know.
- Drag-dropping something else than a proper config file
on Charon sometimes leads to a crash.
- Charon's config files assume that the same volume reference
number is assigned to the same drive every time. For
removables, this is not neccessarily true.
- The Box ST (v1.10) works, but uncheck 'Try EMSI'.
Solving problems:
----------------
Are your address, password and other config items entered right? If the poll proceeds OK without any mail being transferred, that's probably it. Otherwise:
A) use the miniature 'Debug' button to see what exactly is going wrong during a connect. The Debug mode prevents Charon from deleting the outbound packets -- they'll be sent again next time, if you do not delete them yourself.
B) Charon writes its EMSI/YooHoo chatter in a file called SerialLog. You can look at this textfile to see the stuff Charon [r]eads and [w]rites to the serial port.
C) Maybe your boss doesn't like EMSI, force YooHoo only in the Boss Config dialog.
D) Otherwise, change the file type of the config file you use to TEXT and look at it. Maybe there's something wrong? Change it and return the file type back to NDNR. Look at the SYSTEM_NODE line especially if you connect successfully, but don't get any mail from your boss.
E) Fiddle with the following kludges (this is actually not what is going to solve your problems, but anyway): Change the STR resources 128 or 129 using ResEdit. Changing 128 from 1 to 2 gives you a different wake-up sequence, changing 129 from Y to N makes Charon appear in its B/W form on Colour QuickDraw machines. Use this if you find my colour scheme offensive.
If you are checking the SerialLog file, EMSI connects work like this:
Send couple of CRs
-> boss sends EMSI_REQ (if not: fall back to YoHoo, see below)
Send EMSI_INQ
Send point's EMSI_DAT. This contains the data about your setup.
-> boss sends EMSI_ACK twice
-> boss sends EMSI_DAT. Charon currently does not care about the contents.
Send EMSI_ACK twice (or more, unimportant)
After that, it is a matter of sending the mail (not in SerialLog):
Send Zmodem outbound files ('sz filename' in Unix terms)
Send End-of-Zmodem-send (sz NULL)
Receive inbound files (rz)
YooHoo goes like this:
Flush garbage, Send YOOHOO and TSYNC bytes
-> Get ENQ byte (**)
Send 0x1F, a 128 byte data packet, two CRC bytes.
-> Get ACK byte
-> Get YOOHOO (also called YooHoo/2U2)
Send ENQ
-> Get 0x1F, a 128 byte data packet, two CRC bytes.
Send ACK, Do Zmodem sending/receiving.
(**): If you get 2 'C's or NAKs in a row, that indicates a dinosaur. The boss only supports FTS-0001 Xmodem transfers, which are not built into Charon yet. As far as I know, only Tabby falls under this category.
